-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gh104 #106
base: gh33
Are you sure you want to change the base?
Conversation
…rt for rsync daemon on joiner is busy.
// written in BE format. This BE detection has failure probability of | ||
// 1 in 256M. This must be removed after next release. | ||
wsrep_seqno_t const ret(wsrep_seqno_byteswap(seqno)); | ||
return (ret > 0x0000000fffffffffLL || ret < WSREP_SEQNO_UNDEFINED ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a time bomb. It would probably be better to change WSREP_XID_PREFIX and do the byteswap if the stored value has the new format.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does WSREP_XID_PREFIX act as a version ID? If so, then indeed it is better.
…XID prefix as a version ID to distinguish which order XID seqno is stored in.
@@ -317,22 +317,11 @@ trx_sys_print_mysql_binlog_offset(void) | |||
|
|||
#ifdef WITH_WSREP | |||
|
|||
#include <wsrep_xid.h> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This introduces unnecessary dependency between InnoDB and MySQL/wsrep code. Setting xid->formatID = -1
in code below is enough to indicate that the XID is null, so WSREP_*
macros and wsrep_xid_init()
don't have to be included.
Fix to read/write seqno to XID in a little-endian format.